Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference: 465-tree-1
name: 1662
tree-preservation-order: undefined
465-tpo-1
uprn
address-text
point: POINT (-1.023969 50.882894)
geometry: MULTIPOLYGON (((-1.023855 50.882882,-1.023860 50.882904,-1.023876 50.882924,-1.023901 50.882940,-1.023932 50.882951,-1.023967 50.882955,-1.024003 50.882951,-1.024034 50.882941,-1.024060 50.882926,-1.024077 50.882906,-1.024083 50.882884,-1.024077 50.882861,-1.024062 50.882841,-1.024037 50.882825,-1.024005 50.882815,-1.023970 50.882811,-1.023935 50.882814,-1.023903 50.882824,-1.023878 50.882840,-1.023861 50.882860,-1.023855 50.882882)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL